<div id="A-sample-session"></div>
<div class="header">
<p>
Previous: [[cvs: What is CVS not?#What is CVS not?|What is CVS not?]], Up: [[cvs: Overview#Overview|Overview]] &nbsp; |[[cvs: Index#SEC_Contents|Contents]]||[[cvs: Index#Index|Index]]|</p>
</div>

----

<div id="A-sample-session-1"></div>
=== A sample session ===
<div id="index-Example-of-a-work_002dsession"></div>
<div id="index-Getting-started"></div>
<div id="index-Work_002dsession_002c-example-of"></div>
<div id="index-tc_002c-Trivial-Compiler-_0028example_0029"></div>
<div id="index-Trivial-Compiler-_0028example_0029"></div>


As a way of introducing <small>CVS</small>, we&rsquo;ll go through a
typical work-session using <small>CVS</small>.  The first thing
to understand is that <small>CVS</small> stores all files in a
centralized <em>repository</em> (see [[cvs: The Repository#The Repository|Repository]]); this
section assumes that a repository is set up.

Suppose you are working on a simple compiler.  The source
consists of a handful of C files and a &lsquo;<tt>Makefile</tt>&rsquo;.
The compiler is called &lsquo;<code>tc</code>&rsquo; (Trivial Compiler),
and the repository is set up so that there is a module
called &lsquo;<code>tc</code>&rsquo;.

 [[cvs: Getting the source#Getting the source|&bull; Getting the source]]::          Creating a workspace
 [[cvs: Committing your changes#Committing your changes|&bull; Committing your changes]]::     Making your work available to others
 [[cvs: Cleaning up#Cleaning up|&bull; Cleaning up]]::                 Cleaning up
 [[cvs: Viewing differences#Viewing differences|&bull; Viewing differences]]::         Viewing differences

This document was generated on <i>a sunny day</i> using [http://www.nongnu.org/texi2html/ <i>texi2html</i>].
